|
|
HI Kerwin also I upload man.log . please check about this issue. |
|
|
Hi Jason, From the log files, it seems there is an internal error in OTA application. ((BaseDfuAdapter.java:6)#A ]no callback registed) Please check attached picture, even if STB finish discovering services, OTA still fails. There are same errors in log file but OTA disconnect GATT before STB discover service. I think this is why you see incomplete service discovery in airlog. To solve this issue, you should ask OTA application developer to check. Thanks ! |
|
|
hi kerwin Hi kerwin / jason. RCU feedback about mantis 860 ? Please see it on mantis. They did test with BMM-BA02(v1.2) / V15.520.6. below issue happen. 1. according to slowed a Service Discovery ,it can be entered after approximately 45 seconds (in normal cases, within 2 seconds). 2. according to be stopped during processing a Service Discovery ,can't work input of RCU BLE 1. after 45s, can input BLE . Airlog(Lazy Discovery) https://drive.google.com/file/d/19jv7JCEoPF8FxjX_M7BOjpj7ccvQ8_Ot/view?usp=sharing - explnation Frame #7,244~8,395 : Service Discovery since initial pairing (approximately 1 second) Frame #23,779~25,157 : OTA enter 1st times (about 1s , BLE KEY Input Normal) Frame #46,054~48,063 : OTA enter 2nd times (about 2s , BLE KEY Input Normal) Frame #61,188~71,126 : OTA enter 3rd times (about 2s , BLE KEY Input Normal) Frame #76,733~78,052 : OTA enter 4th times (about 2s , BLE KEY Input Normal)) Frame #89,545~91,772 : OTA enter 5th times (about 2s , BLE KEY Input Normal) Frame #103,501~138,078 : OTA enter 6th times (about 45s, after 45s, BLE Key Inptut OK) 2. according to be stopped during processing a Service Discovery ,can't work input of RCU BLE ( it seem RCU send BLE Key in airlog) https://drive.google.com/file/d/1ie2Yx-7WWUSy90hBm1cIco0XGvExVYyR/view?usp=sharing - explanation Frame #3,680~4,816 : Service Discovery since initial pairing (about 1s) Frame #17,745~20,799 : OTA enter 1st times (about 4s, all service didn’t do discovery but BLE Key input is ok.) Frame #60,069~62,610 : OTA enter 2nd times (about 3s, BLE Key input is ok) Frame #75,628~77,588 : OTA enter 3rd times (about 2s, BLE Key input is ok) Frame #98,117~100,154 : OTA enter 4th times OTA 진입 4 회(about 2s, BLE Key input is ok) Frame #113,030~115,199 : OTA enter 5th times (about 3s, BLE Key input is ok) Frame #127,246~130,338 : : OTA enter 6th times (about 4s, BLE Key input is ok) Frame #141,851~181,317 : OTA enter 7th times (about 4s, BLE Key input is ok) Frame #191,358~193,452 : OTA enter 8th times (about 2s, BLE Key input is ok) Frame #205,360~229,183 : OTA enter 9th times (about 33s, Service Discovery is stopped, BLE KEY input don’t work) Frame #246,724~246,758 : STB restarts Service Discovery but it is terminated and BLE Key don’t work. |
|
|
hi kerwin it isn't same time regarding to Upper log. but you can see a sequence. and see another log. OTA enter, BLE key don't work (STB Log) https://drive.google.com/file/d/1fVNcVqCdB-ivz01ozHhbtOs6lydmp0AP/view?usp=sharing (BLE Log) https://drive.google.com/file/d/129toicvVZlWoqkIeyg5PvnAzA_lpEeVM/view?usp=sharing OTA enter , BLE KEY is ok. (STB Log) https://drive.google.com/file/d/1drHaxLTmBlJoEvgFhBtI5RYbyBfIGadZ/view?usp=sharing (BLE Log) https://drive.google.com/file/d/1KhC1A_PK8-ZoVhabIhutNcOeazgl2CwX/view?usp=sharing |
|
|
Hi Jason, The log you provided is not for "Service Discovery Disorder" issue, right ? Is it for another issue about BLE key not working during OTA ? |
|
|
hi kerwin this request is BLE key don't work or work for BLE KEY input too late since Sequence Discovery process. today I receive additional request as below. STB has problems in discovery of RCU's service in entering OTA intermittently, and in the case of Android smartphone OTA App, when only connect to three devices (battery, PNPID, and OTA Service), do deal with Service Discovery. please see a picture. so RCU is already connected between STB and RCU when accessing OTA via Hidden Menu and all services have been discoveryed, so it doesn't seem necessary to re-discovery when entering OTA separately, is it possible to modify this part in STB's iSet App? < current > When accessing OTA via Hidden Menu, Request all Service Discovery (During Re-Discovery is failed, RCU BLE don't work) < Request for modification > When accessing OTA via Hidden Menu, Only request a Discovery for Battery , PNP ID, OTA Service(0xfff1, 0xffd2, oxffe0) Connect to android OTA Web Device(Samsung Note 8(Android 9) / BMM-BA02(v1.2)) Airlog https://drive.google.com/file/d/1x-fki5a8w5tmHe-4bkNZJwA2e0HvwOIS/view?usp=sharing serviceDiscovery.jpg (156,566 bytes) |
|
|
Hi Jason, >>is it possible to modify this part in STB's iSet App? RCU OTA is not included in iSet APP. You should pass this request to RCU OTA APP develop company. Please check again. Thanks ! |
|
|
hi kerwin I think so.. I also check it with RCU Company. Thanks |
|
|
hi kerwin Let me know an owner about a management of Service Discovery for OTA. I think it is responsible by MW. if it is wrong , please correct it. 1. when enter OTA of RCU if Service Discovery is proceed very too late( a few second ~ a few ten seconds), RCU BLE don't work during proceeding for Discovery in OTA. https://drive.google.com/file/d/1IxPHKGiASGLJ4rin4TZCrrm5ge3JodbM/view?usp=sharing (STB log) item 1 issue .. it happen in Remote solution RCU. 2. when Service Discovery is stopped in OTA, RCU BLE don't work. https://drive.google.com/file/d/1_NoGFuGVLWElXshowSqFxkOFiMbHJIog/view?usp=sharing (STB log) after upper step (RCU BLE don't work), if try to find RCU with using CH- Key, RCU is recovered via Discovery working again. https://drive.google.com/file/d/1BMwYIhS1J-DVdpvmMVHxgIT-NPUXH0wp/view?usp=sharing (STB Log) Thanks. |
|
|
this issue is monitored by BTVD-9947 for next HomeUI 5.2.2. |
|
|
Hi Jason, Per replied before, OTA process is handled by OTA app. Please ask OTA developer to review log first. Thanks ! |
|
|
HI Kerwin according to skb manager and RCU company comment , other box don't have same problem in other box(AI2, AOSP). So after check a log , investigate BT stack part about this issue. Thanks. |
|
|
hi kerwin as we talked it yesterday, please start to debugging about this issue later after solve a high priorty issues. Thanks |
|
|
Hi Jason, Please check review result as below: 1. main_log_200804_BFX_AT100_v15_520_8_BMM_BA02_Lazy_Service_Discovery.log ==> From the log, BLE keys don't work because of idle timeout. 08-04 10:14:27.006 4133 4133 V OTA : [ (BaseDfuAdapter.java:1)#A ]notifyStateChanged 0x0400 >> 0x1000 08-04 10:14:27.006 4133 4133 D PopupHiddenMenuRemoteUpdate2: onStateChanged : 4096 08-04 10:14:27.007 4133 4133 V OTA : [ (BaseDfuAdapter.java:1)#A ]notifyStateChanged 0x1000 >> 0x0800 08-04 10:14:27.008 4133 4133 V OTA : [ (BaseDfuAdapter.java:6)#A ]no callback registed 08-04 10:14:27.008 4133 4133 V OTA : [ (GlobalGatt.java:6)#DisconnectGatt ]disconnect : 40:19:20:00:00:01 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ OTA APP disconnect GATT, and then after 10s, STB reconnect to RCU again after 10s...... 08-04 10:14:37.797 17261 17262 D kernel : <6>[58702.615245@3] input: BMM_BA02_001 as /devices/virtual/misc/uhid/0005:005D:0002.002D/input/input49 2. main_log_BFX_AT100_v15_520_8_BMM_BA02_OTA_ServiceDiscovery_Stop.log ==> It is similar with previous log, OTA APP disconnect GATT because of "no callback registered". It should be checked by OTA APP developer. 08-04 11:08:41.579 4122 4122 V OTA : [ (BaseDfuAdapter.java:1)#A ]notifyStateChanged 0x0400 >> 0x1000 08-04 11:08:41.579 4122 4122 D PopupHiddenMenuRemoteUpdate2: onStateChanged : 4096 08-04 11:08:41.580 4122 4122 V OTA : [ (BaseDfuAdapter.java:1)#A ]notifyStateChanged 0x1000 >> 0x0800 08-04 11:08:41.580 4122 4122 V OTA : [ (BaseDfuAdapter.java:6)#A ]no callback registed 08-04 11:08:41.581 4122 4122 V OTA : [ (GlobalGatt.java:6)#DisconnectGatt ]disconnect : 40:19:20:00:00:01 3. main_log_200804_BFX_AT100_v15_520_8_BMM_BA02_Lazy_n_Version_Mismatch.log ==> RCU is disconnected due to 10s idle timeout. And then STB reconnects to RCU successfully. Hence BLE key works well again. I have no idea why idle timeout happens from the log file. |
- yk.jung ( (ALTech) Younkwang Jung ) developer
